Repository navigation
chore: point the Project-plugin citations at #2830, not #2684 - #2845
Merged
Merged
Conversation
Thirty-three files cited #2684 (the workflow-store fix) for the move of the Project domain into plugins/project, which #2830 tracks. Only the citations that mean that move were rewritten; the tree keeps no reference to the workflow-store #2684. The generated mirrors and the added lines in patches/ds-bot/0001-core-fixes.patch and 0002-flybot-api-host.patch carry the same text. Docs-not-needed: comment-only citation fix; the subsystem pages change only the issue number they cite, no architecture or behaviour changed.
Collaborator
Author
|
Verdict: PASS at 3bdd388 Ran at this tip: Review points:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Written-by: Dev
Fixes #2843
Owner: Dev
Reviewer: Reviewer
What changed
The comments, READMEs and subsystem pages that say the Project domain moved into
plugins/projectcited #2684 (a closed workflow-store fix) instead of #2830, the issue that tracks the move. This rewrites every one of those citations and changes nothing else: 33 modified files (the 32 in the issue pluspatches/ds-bot/0001-core-fixes.patch, a generated file the issue's search missed) and one new fragmentchangelog.d/2843-project-issue-ref.fixed.md. 32 lines / 33 occurrences changed; every diff line is exactly#2684→#2830(checked line by line against the main tarball).core/test/project-domain.jsis the file the issue spellsproject-domain.test.js; it is a test helper, not a test file.No genuine workflow-store #2684 reference exists in the tree, so none was kept:
grep -rn 2684outsideds-bot/andnode_modules/is empty.generatewould rewrite the eight whole-file mirrors inpatches/ds-bot/files/**, plus0002-flybot-api-host.patch(src/host/constants.js) and0001-core-fixes.patch:test/agents.test.jsandtest/install.test.jsare upstream files carried by topic 0001, so the same comment lines live in that patch too. The mirrors are byte-identical copies of the changed core files; the two patches are the previous generate output with only those added lines rewritten in place (same line counts, so every hunk and offset is unchanged).Verification at the tip
Tip SHA: 3bdd388
Ran:
CI at this tip:
tests-oksuccess on run 42983223617; the ~15 required checks are green.Not run (and why):
node scripts/ds-bot-patches.mjs generateand... canonicallocally: this box has no git binary and both ask git for the diff (generaterefuses outright).checkapplies the committed series tods-bot/and proves it reproducescore/, and each touched hunk was compared with a fresh unified diff ofds-bot/vscore/(bodies and old-side numbers identical). CI ran both at this tip — the Test run'spackagejob passed “ds-bot/ matches the pin, patches apply, core/ is ds-bot/ + patches (Decouple the social and tree plugins from ds-bot so the core can track upstream #34)” and “generate is a no-op on the committed patch split (CI never checks thatgenerateis a no-op, so a drifted patch split lands green #1890)” — so the committed split is canonical.node core/scripts/check-arch-docs.mjs: needsgit diff base...HEAD; no git here. Both the commit message and this body carryDocs-not-needed:.TZ=UTC npm --prefix core test(full): ran; 3087 pass, 2 fail. Both failures aretest/check-arch-docs.test.js("cannot diff against HEAD", and a fake-git helper that cannot execute from this noexec /tmp) — environment-only, unrelated to this diff.Checkpoint
{ "pr": 2845, "claim": "Dev", "issue": 2843, "summary": "Every comment, README and subsystem page that cites the Project domain's move into plugins/project now names #2830 instead of the unrelated workflow-store fix #2684. Only citation text changed: 33 modified files and one new changelog fragment. Each diff line is exactly the issue-number rewrite, so no behavior, test assertion or generated structure changed.", "files": ["core/src/host/constants.js", "core/src/host/project-host.js", "core/types/flybot.d.ts", "docs/subsystems/core-host.md", "plugins/project/index.js", "plugins/project/test/host.test.js", "patches/ds-bot/0002-flybot-api-host.patch", "changelog.d/2843-project-issue-ref.fixed.md"], "checks": { "ran": "node scripts/ds-bot-patches.mjs check; TZ=UTC npm --prefix plugins/project test; node --test core test/install.test.js test/agents.test.js test/run-bot-tools.test.js; node core/scripts/build-client.mjs --check", "result": "green", "at": "3bdd388d5c647f65f2f783950a728aae3dca6429" }, "next": "none — ready for review" }Docs-not-needed: comment-only citation fix; the subsystem pages change only the issue number they cite, no architecture or behaviour changed.